[SDK-1696] Allow caller of cache.get to specify an expiry time adjustment #491
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The adjustment value used on the expiry time from the cache can now be configured per call to
cache.get
. The default is 0.This allows:
expires_at
to be the same time asnow() + expires_in
(no longer includes an adjustment built in)getTokenSilently
can itself make a decision about whether to use the cached value, or refresh the token ifexpires_in - adjustment < now
isAuthenticated
to returntrue
right up until theexpires_in
time is reachedReferences
Fixes #480
Fixes #474
Testing
Checklist
master